-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix FE issues - texts, translations, styles #1777
Conversation
@@ -162,7 +162,7 @@ export default function CampaignNewsSection({ campaign, canCreateArticle }: Prop | |||
const { t, i18n } = useTranslation('news') | |||
const { small }: { small: boolean } = useMobile() | |||
|
|||
const INITIAL_HEIGHT_LIMIT = 200 | |||
const INITIAL_HEIGHT_LIMIT = 203 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
src/pages/terms-of-service.tsx
Outdated
@@ -4,7 +4,7 @@ import { serverSideTranslations } from 'next-i18next/serverSideTranslations' | |||
|
|||
export const getStaticProps: GetStaticProps = async ({ locale }) => ({ | |||
props: { | |||
...(await serverSideTranslations(locale ?? 'bg', ['common'])), | |||
...(await serverSideTranslations(locale ?? 'bg', ['common', 'validation', 'auth'])), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
validation namespace doesn't seem to be needed.
If this change is regarding the missing translations of subscription modal, consider adding translations to those fields in the common namespace. Otherwise we would need to visit page by page, to see whether that particular page imports the auth namespace, as the subscription modal is available to all pages thru the footer.
No description provided.